Circuit breakers

Circuit breaking settings can be specified individually for each defined priority. How the different priorities are used are documented in the sections of the configuration guide that use them.

{
  "default": "{...}",
  "high": "{...}"
}
default
(optional, object) Settings object for default priority.
high
(optional, object) Settings object for high priority.

Per priority settings

{
  "max_connections": "...",
  "max_pending_requests": "...",
  "max_requests": "...",
  "max_retries": "...",
}
max_connections
(optional, integer) The maximum number of connections that Envoy will make to the upstream cluster. If not specified, the default is 1024. See the circuit breaking overview for more information.
max_pending_requests
(optional, integer) The maximum number of pending requests that Envoy will allow to the upstream cluster. If not specified, the default is 1024. See the circuit breaking overview for more information.
max_requests
(optional, integer) The maximum number of parallel requests that Envoy will make to the upstream cluster. If not specified, the default is 1024. See the circuit breaking overview for more information.
max_retries
(optional, integer) The maximum number of parallel retries that Envoy will allow to the upstream cluster. If not specified, the default is 3. See the circuit breaking overview for more information.

Runtime

All four circuit breaking settings are runtime configurable for all defined priorities based on cluster name. They follow the following naming scheme circuit_breakers.<cluster_name>.<priority>.<setting>. cluster_name is the name field in each cluster’s configuration, which is set in the envoy config file. Available runtime settings will override settings set in the envoy config file.